Posted on LinkedIn March 30, 2026
Here is the updated post with the new sources and the Oracle statistic integrated:
Being responsive is not the same as being decisive
There is a version of staying accessible that feels like good leadership and quietly works against it.
You respond quickly. You are across everything. Your team knows they can reach you and get an answer. Nothing sits too long without your attention. From the outside, this looks like engagement and commitment. Inside the decision-making process, something different is happening.
When input flows in without a filter, it does not just inform your judgment. It starts to replace it.
How input takes over
Every piece of incoming information carries more than content. It carries framing, urgency signals, and an implicit ask. An escalation framed as urgent tells you that something needs immediate attention, whether it actually does or not. A request presented with a clear recommendation makes that recommendation the default unless you actively resist it. A problem brought to you by a senior stakeholder carries a different weight than the same problem brought by someone more junior, even when the substance is identical.
None of this is manipulation. It is just how communication works. People frame their messages to get what they need. That is reasonable. The problem is on the receiving end, when a leader processes that input without first asking whether the framing matches the reality.
Leaders who operate in a reactive mode are not making decisions based on their own assessment of what matters. They are making decisions based on who showed up most recently, who framed their issue most compellingly, and whose urgency signal was strongest. The result looks like responsiveness. It produces something closer to being directed by whoever has the best access and the sharpest elbows.
Research by Oracle and behavioural economist Seth Stephens-Davidowitz puts this in concrete terms. Their study found that 85% of business leaders report experiencing decision stress, and three-quarters say their daily decision volume has increased tenfold over the last three years. That volume is not neutral. It creates the exact conditions where input starts driving judgment rather than informing it, because the cognitive load required to evaluate each decision on its own merits simply isn’t available when the volume is that high.
Roy Baumeister’s research on decision fatigue explains the mechanism. His work established that the capacity for self-regulation, which includes the judgment required to evaluate competing inputs and make considered decisions, is a finite cognitive resource that depletes with use. As decision volume increases over the course of a day, the quality of subsequent decisions degrades. Leaders processing high volumes of incoming input without filtering are not just making reactive choices. They are making reactive choices with diminishing cognitive resources, the longer the day runs. (Baumeister et al., “Ego Depletion: Is the Active Self a Limited Resource?”, faculty.washington.edu/jdb/345/345%20Articles/Baumeister%20et%20al.%20(1998).pdf)
The cost that doesn’t show up immediately
The effect of letting input drive judgment rarely announces itself clearly. It shows up in patterns that develop over weeks and months.
Your decisions are starting to feel inconsistent with the team. Not because your judgment changed, but because the framing of incoming information changed. A priority that held firm on Monday gets quietly revised after a stakeholder conversation on Thursday. The team can no longer predict how you will respond to similar situations because your response depends on the context they weren’t present.
Your actual strategic priorities get crowded out. Not abandoned, just perpetually deferred. The work that would move the organization forward in a meaningful way keeps slipping to next week because this week’s incoming volume keeps generating decisions that feel urgent and are rarely important.
And your capacity for the decisions that genuinely require your judgment shrinks. The high-stakes calls, the ones where your experience and perspective produce something the team genuinely cannot produce without you, get whatever cognitive resources remain after the incoming volume has been processed.
Harvard Business School professor Francesca Gino’s research on cognitive fatigue makes this practical. Her work shows that decision quality degrades measurably as mental load accumulates over the day, with leaders increasingly defaulting to familiar patterns and fast responses rather than to considered judgment. The implication is structural: when and how decisions reach you matter as much as the decisions themselves. (Gino, “Don’t Make Important Decisions Late in the Day,” HBR, hbr.org/2016/02/dont-make-important-decisions-late-in-the-day)
The difference between responsiveness and decisiveness
Responsiveness is about the speed of acknowledgment. It signals that you are present, that people can reach you, and that issues will not sit unaddressed indefinitely. Those are real leadership values worth maintaining.
Decisiveness is different. It is about the quality of the judgment behind the response, not the speed of the response itself. A fast answer that reflects the last person’s framing rather than your own assessment is not a decision. It is an echo.
Leaders who confuse the two tend to optimize for the first at the cost of the second. They pride themselves on a fast response time while not noticing that their response quality has drifted, that they are no longer deciding so much as processing and relaying.
The structural solution is not to become less accessible. It is to build a filter between the incoming input and your decision-making process. That filter does not need to be complicated. It requires asking three questions before responding to any significant incoming ask.
Does this require a decision, or does it require acknowledgment? Many things that arrive as decisions are actually updates. They need to be heard and noted, not resolved on the spot. Treating them as decisions inflates your decision volume without adding value.
Is this mine to decide, or has ownership landed at the wrong level? A large proportion of what escalates to senior leaders does so not because it genuinely requires their judgment, but because ownership at a lower level was never clearly defined. If the right owner exists, the response is to route it back rather than absorb it.
Does acting on this advance a strategic priority, or does it just close an open loop? Closing open loops feels productive. It is sometimes just an activity. The decisions worth your judgment are the ones that move something important forward, not the ones that simply remove something from your inbox.
What protected judgment looks like in practice
Leaders who protect their judgment from input overload do not do it through willpower. They do it structurally.
They create predictable windows for different types of decisions rather than processing everything as it arrives. High-stakes calls get protected time earlier in the day when cognitive resources are strongest. Routine responses get batched. Escalations get filtered before they reach the decision-making level.
They establish explicit criteria for what escalates to them and what doesn’t. Not as a way to be less available, but as a way to ensure the things that do reach them are the things that genuinely benefit from their judgment.
They slow down slightly before responding to anything framed with urgency. Not to cause delay, but to ask whether the urgency is real or a feature of how the request was packaged. The two are frequently not the same thing.
None of this makes a leader less responsive in the ways that matter. It makes their responses more valuable because the judgment behind them has been protected rather than depleted.
Responsiveness is a communication standard. Decisiveness is a cognitive discipline. Both matter, and they require different kinds of protection.
Sources
Roy F. Baumeister et al., “Ego Depletion: Is the Active Self a Limited Resource?” Free full text available at: faculty.washington.edu/jdb/345/345%20Articles/Baumeister%20et%20al.%20(1998).pdf
Francesca Gino, “Don’t Make Important Decisions Late in the Day” Harvard Business Review, 2016. Available at: hbr.org/2016/02/dont-make-important-decisions-late-in-the-day
